From: squirrel@echelon.alias.net (The Tech Lion)
Subject: FZ BIBLE - LEVEL 3 COURSEPACK [3/7]
Date: 15 Nov 1999 00:00:00 GMT
Message-ID: <3a5fa6d12f911ca51520b2b62e052ec8@anonymous.poster>
Sender: Secret Squirrel <squirrel@echelon.alias.net>
Organization: FreeZone Bible Association
Mail-To-News-Contact: postmaster@nym.alias.net
Comments: Please report problems with this automated remailing service to <squirrel-admin@echelon.alias.net>. The message sender's identity is unknown, unlogged, and not replyable.
Newsgroups: alt.religion.scientology,alt.clearing.technology

FREEZONE BIBLE ASSOCIATION TECH POST

ACADEMY LEVEL III COURSEPACK: Part 3 of 7

***************************************

Continuing our quest to spread the Tech on the internet,
we bring you the Academy Level 3 coursepack from the late
1980s, in 7 parts.

The full table of contents is in Part 1 only.

To see the proper formatting, use a fixed-pitch font such as
Courier to view this file.

Looking forward to a Tech-filled Millenium,

-The Tech Lion 

********************

STATEMENT OF PURPOSE 

Our purpose is to promote religious freedom and the Scientology
Religion by spreading the Scientology Tech across the internet.

The Cof$ abusively suppresses the practice and use of
Scientology Tech by FreeZone Scientologists.  It misuses the
copyright laws as part of its suppression of religious freedom.

They think that all freezoners are "squirrels" who should be
stamped out as heretics.  By their standards, all Christians, 
Moslems, Mormons, and even non-Hassidic Jews would be considered
to be squirrels of the Jewish Religion.

The writings of LRH form our Old Testament just as the writings
of Judaism form the Old Testament of Christianity.

We might not be good and obedient Scientologists according
to the definitions of the Cof$ whom we are in protest against.

But even though the Christians are not good and obedient Jews,
the rules of religious freedom allow them to have their old 
testament regardless of any Jewish opinion.  

We ask for the same rights, namely to practice our religion
as we see fit and to have access to our holy scriptures
without fear of the Cof$ copyright terrorists.

We ask for others to help in our fight.  Even if you do
not believe in Scientology or the Scientology Tech, we hope
that you do believe in religious freedom and will choose
to aid us for that reason.

Thank You,

The FZ Bible Association

************************

PART 3

 7. HCOB   21 Apr. 1970       2-Way Comm C/Ses

 8. HCOB    3 July 1970       C/Sing 2-Way Comm
                              C/S Series 14

 9. HCOB   17 Mar. 1974       Two-Way Comm, Using Wrong Questions

10. HCOB   19 Dec. 1980R      Rehab Tech


******************************************************************

7. HCOB   21 Apr. 1970       2-Way Comm C/Ses


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

      HCO BULLETIN OF 21 APRIL 1970

Remimeo

            2-WAY COMM C/Ses


There are four main reasons why a Case Supervisor or an auditor 
gives a "2-way comm" C/S.

1. WHEN NOT ENOUGH DATA TO C/S. "2-way comm to obtain data about 
case progress and status."

2. WHEN PC INFERS SOMETHING IN CASE THAT'S NOT BEEN HANDLED. "2-
way comm to find what pc thinks should be handled on case."

3. WHEN PC HASN'T COGGED ON END RESULT. "2-way comm on (process 
just run) to see what thoughts pc had regarding it."

4. WHEN PC'S POST PURPOSE IS BEING CLEANED UP. "2-way comm on how 
his post purpose fits into org -- or if he can do it."

In all these instances the C/S may be as specific as he likes 
about what he wants asked or cleared up. In other words, the 
quoted C/Ses above are only examples. Each of the above four 
general types can have a great number of different questions. The 
C/S must be very familiar with the four types given in capitals 
above.

On his part, the auditor can vary the C/S's question around to 
get different slants on it. The auditor doesn't have to get an 
F/N on the 2-way comm session but often does.

The auditor can introduce a curve, an alter-is, by Q and A with 
the pc and by evaluation.

The drill on 2-way comm is the old ask and listen.

A Q and A is of course echoing the pc's statement. Example: Pc: 
"I never liked my father." Auditor: "What about your father?" Pc: 
"He was cruel." Auditor: "What about cruel people?" Pc: "I don't 
like them." Auditor: "What else don't you like?" And so on and 
on.

A correct session is for the auditor to hold to the C/S's main 
line of questioning no matter how he phrases it and listen to and 
write down what the pc says.

Evaluation in auditing 2-way comm is the other deadly sin. The 
auditor asks and listens. He doesn't explain anything to the pc. 
Example: Pc: "I didn't dig the process." Auditor: "Well, you see, 
that process was intended to ..." and here we go on evaluation. 
Even an auditor's facial expression can be evaluation.

Ask and listen and ack. Prompt only by varying the original 
question now and then, that's what the good 2-way comm auditor 
does.

               WORKSHEETS

The 2-way comm worksheet is rather more detailed as to what the 
pc says than process worksheets.

The C/S needs the data.

Or in looking it over the auditor himself, if he's his own C/S, 
will need the data.

The questions the auditor asks should be noted on the worksheet 
as a guide.

                 MAXIM

It is a C/S maxim "when in doubt order a 2-way comm."

          2-WAY COMM AUDITOR

Any auditor can 2-way comm. Saint Hillers were best at it. 
Academy level auditors can be used in this, even Dianetic 
auditors.

The only reservation is not to assign an auditor whose grade is 
lower than the pc's. The auditor's class is not as important as 
his grade. The reason for this is that the OT pre-OT, in being 2-
way commed by a Grade V, can blow the poor auditor apart or can 
be stuck with a data withhold.

                METER

All 2-way comm is of course done on a meter. It is, however, not 
a Sec Check or Prepcheck. TA position and needle reaction and 
F/Ns are important to the C/S.

One doesn't 2-way comm past an F/N, cog and VGIs.


L. RON HUBBARD
Founder

LRH:dz.ei.rd.gm



******************************************************************

8. HCOB    3 July 1970       C/Sing 2-Way Comm
                             C/S Series 14


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

      HCO BULLETIN OF 3 JULY 1970

Remimeo

            C/S Series 14

          C/Sing 2-WAY COMM


The C/S is liable to make most of his C/S errors in C/Sing 2-Way 
Comm.

The reasons for this are

1. Two-way comm IS auditing.

2. The errors that can be made in any auditing can be made in
   2-way comm.

3. Untrained or poorly-trained auditors do not always respect
   2-way comm as auditing.

4. Errors in 2-way comm become masked since the procedure is 
   loose.

5. Earlier C/Ses on the case may have missed the easily missed
   2-way comm errors.


      RULES OF C/Sing 2-WAY COMM

A. The C/S must recognize that 2-way comm is auditing. Therefore, 
it follows all the rules of auditing.

B. Any error that occurs in other auditing can occur in 2-way 
comm auditing. Errors in a 2-way comm session must be carefully 
looked for as they easily can be masked in the worksheet.

C. Auditors must be persuaded by the C/S to make notation of 
auditing essentials in 2-way comm as of senior importance to pc's 
text (which is also made note of in the worksheet).

D. The questions asked in 2-way comm can be very incorrect just 
as rote processes can be.

E. An auditor must be trained as a 2-way comm auditor (Class II). 
Otherwise, he will evaluate, Q-and-A and commit other faults.

F. If an ARC break occurs early in a 2-way comm session and is 
not handled as such, the rest of the session is audited over an 
ARC break and can put a pc into a sad effect.

G. A pc with a PT problem not being handled in the 2-way comm 
will get no gain.

H. A pc with a W/H in a 2-way comm session will become critical, 
nattery and/or get a dirty needle.

I. Two-way comm processes must be flattened to F/N. If an F/N 
doesn't occur, then the subject didn't read in the first place or 
the auditor Q-and-Aed or evaluated or changed the subject or the 
TRs were out or the pc's ruds were out.

J. A 2-way comm subject chosen must be tested for read in that 
session before being used for 2-way comm.

K. Improper 2-way comm questions can plunge the pc into an out-
rud situation not then handled. "Is anything upsetting you?" or 
any mention of upsets by the auditor is the same as asking for an 
ARC break. "Has anything been troubling -- worrying you lately?" 
is the same as asking for a PTP. "Who aren't you talking to?" is 
asking for W/Hs.

L. The subject of major processes should be kept out of 2-way 
comm C/Ses, auditors' questions and 2-way comm assessment lists 
(ARC breaks, problems, overts, changes or any major auditing 
subject, as they are too heavy, being the buttons of the bank).

M. The C/S should only let Class II or above auditors do 2-way 
comm sessions.

N. A rud going out in a 2-way comm session must be put in by the 
auditor.

O. A 2-way comm session should end in an F/N.

P. Auditors whose 2-way comm sessions do not end in F/N must be 
taught to check the subject for read before using, not to Q-and-
A, not to evaluate, and given a refresher on 2-way comm tapes and 
HCOBs.

Q. In a 2-way comm session that flubs, the C/S must be careful to 
isolate the errors just as in any other auditing session that 
flubs and put them right.

R. A 2-way comm subject that reads on test and doesn't F/N on 2-
way comm must be checked for O/R (if TA went up) and rehabbed by 
the 1965 rehab method, or prepchecked or just continued.

                 --------

The whole point to all of this is that a 2-way comm session IS 
auditing. It is delivered by the auditor, C/Sed and remedied like 
any other session.

Also it is usually being run on a delicate pc who is more 
affected by errors than pcs being given other processes.


L. RON HUBBARD
Founder

LRH:sb.rd.gm



******************************************************************

9. HCOB   17 Mar. 1974       Two-Way Comm, Using Wrong Questions


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

      HCO BULLETIN OF 17 MARCH 1974

Remimeo

         TWO-WAY COMM CHECKSHEETS

    TWO-WAY COMM, USING WRONG QUESTIONS


Two-way comm is not an art. It is a science which has exact 
rules.

Foremost in the rules is

   DON'T USE A LISTING QUESTION IN TWO-WAY COMM.

By a "listing question" is meant any question which directly or 
indirectly calls for items in the pc's answer.

Use of "who," "what," "which," instantly turns a two-way comm 
into a listing question.

Listing questions are governed by the rules of listing and 
nulling.

If you use a listing question accidentally in two-way comm, you 
can get the same bad reactions from a pc that you would get on a 
wrongly done list.

The reason for pc upsets in two-way comm is hidden, as it is not 
apparently a listing process, rarely gets the correction a bad 
list would get.

Asking "who" or "what" or "which" during a two-way comm after the 
main question can also turn it into a listing and nulling process.

Two-way comm questions MUST be limited to feelings, reactions, 
significances. They must NEVER ask for terminals or locations.

EXAMPLE: "Who upset you?" in two-way comm causes the pc to give 
items. This is a LIST. "What are you upset about?" does the same 
thing. "Which town were you happiest in?" is also a LISTING 
question, NOT a two-way comm question. Any of these result in the 
pc giving items. They are not then nulled or correctly indicated. 
The pc can get VERY upset just as he would with a wrong list. Yet 
the session is not a "listing session" so never gets corrected.

EXAMPLE: "How are you doing lately?" is an example of a correct 
two-way comm question. It gets off charge and gets no list items. 
"Are you better these days than you used to be?" "How have you 
been since the last session?"

"What happened" is different than "What illness," "What person," 
"What town," which are listing questions.

                REPAIR

When other things fail to locate the upset of a pc look into two-
way comm processes in the folder and treat them as L&N processes 
where the pc has answered with items. The relief is magical.


L. RON HUBBARD
Founder

LRH:ntm.rd.gm



******************************************************************

10. HCOB   19 Dec. 1980R      Rehab Tech


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

    HCO BULLETIN OF 19 DECEMBER 1980R
        REVISED 16 NOVEMBER 1987

Remimeo
Tech/Qual
Academies
Class III Auditors
  and above


              REHAB TECH

  Refs:
  HCOB 30 June 65    RELEASE, REHABILITATION OF,
                     FORMER RELEASES AND THETAN
                     EXTERIORS
  HCOB 21 July 65    RELEASE REHABILITATION
  HCOB  2 Aug. 65    RELEASE GOOFS
  HCOB 11 Feb. 66R   FREE NEEDLES, HOW TO GET
    Rev. 22.2.79     THEM ON A PC
  HCOB 26 Aug. 68    REHAB AND CORRECTION
  HCOB  5 Dec. 71    END PHENOMENAS
    Reiss. 21.9.74
  HCOB 15 Nov. 78    DATING AND LOCATING
    Reiss. 7.7.86
  E-Meter Instruction Film 4, How the E-Meter Works


This bulletin is a condensation of the tech I first developed in 
1965 on the subject of rehabs and release.

While there is considerably more data on these subjects in the 
Technical Volumes and on the Class VIII tapes, this issue sets 
forth the key data and presents the methods for rehabbing in one 
consolidated issue for the first time.

DEFINITIONS:

"Rehab" is a shortened version of "rehabilitate," which means: to 
restore to a former capacity or condition.

"Release" is the term for what occurs when a person separates 
from his reactive mind or some part of it or when he separates 
from some mass.

In Scientology we use the term "rehabilitate" most commonly to 
mean: restoring a state of release previously attained by the pc.

                RELEASES

Scientology processes can be categorized as follows:

1. Those processes which direct the preclear's attention to the 
mental masses in his reactive mind in order to enable him to 
separate out from them.

2. Those processes which are aimed at increasing the preclear's 
abilities.

Both types of processes lead to release.

Both types of processes are necessary to bring a person up the 
levels of awareness and up each step of the Grade Chart to OT.

When you take a thetan out of a mass, that's a release.

When you erase the mass and leave the thetan there, that's an 
erasure. Erasure is a different phenomenon from release.

In auditing, when the pc spots something in the bank he 
disconnects from the bank to a greater or lesser degree. That is 
a release. Or when the pc becomes free of a difficulty or 
personal "block" or inability stemming from the mind, that is a 
release.

A person can and does go release many times in the course of his 
auditing. He may go release many times while being run on the 
processes of a grade before he attains the ability of that grade.

The Grades Releases are covered fully in HCOB 22 Sept. 65, 
RELEASE GRADATION, NEW LEVELS OF RELEASE, in HCOB 27 Sept. 65, 
RELEASE GRADATION, ADDITIONAL DATA, and on the Grade Chart 
itself. Further data can be found in HCOB/HCO PL 23 Oct. 80R II, 
CHART OF ABILITIES GAINED FOR LOWER LEVELS AND EXPANDED LOWER 
GRADES.

Oddly enough, the idea of release can translate through to the pc 
to include releases in life too. For example, a person was in 
prison and then was let out. This might well read as a release if 
he was asked about former releases, and it would be okay. One 
sees how this can be in view of the basic concept of release, 
e.g., when you take a person out of a mass -- any mass -- that is 
a release.

So "release" points in life such as the above are valid and, 
though one doesn't ask for them specifically, should they come up 
during a former-release rehab on a pc, they are to be handled.

However, the auditor must understand that such a release in no 
way means that a person is a release on a process or on one of 
the grades! Prison might be a problem to someone but getting out 
doesn't make him a Problems Release! Don't misconstrue one for 
the other and declare someone a Grades Release at some level 
because he had a release in life.

Actually, one can go release on any subject and theoretically one 
could rehab any release a pc had. The exact subjects a pc must be 
released on in order to make it up the Bridge are those listed on 
the Grade Chart.

                 OVERRUN

Overrun occurs when the thetan considers that something has gone 
on too long or happened too often.

When the person begins to feel this way about something, he 
begins to protest it and try to stop it. This tends to make 
things more solid and builds up mass in the mind. People who are 
very intent on stopping things in life appear solid and massy.

In auditing, an overrun means the preclear came out of the bank 
and then went back into it again. For instance, the pc released 
on the process "From where could you communicate to your dog?" 
but the auditor continued the process after he should have 
indicated the F/N and gone on to something else. By continuing, 
the auditor throws the pc back into the bank again and wrecks the 
release state.

An overrun in auditing can also mean that the pc gained an 
ability to do something and the auditor continued the process or 
grade past the point where the ability had been regained. By 
pushing on, the ability can get invalidated. In both cases the 
person's attention goes back onto his case and hangs up. The 
person can feel the mass of it again.

In life when something is overrun, the person begins to 
accumulate protests and upsets about the thing or activity he 
feels overrun on. His attention tends to stick on it. This also 
builds up mass.

An overrun, whether it occurred in auditing or in life, is 
handled in auditing using the tech of rehabbing.

            THEORY OF REHABBING

The theory of rehabs is based on the following stable datum: This 
particular universe is built by twos. One cannot know a datum 
unless there is another datum to compare it to. This fact can 
also be seen to operate in the field of the mind. (Ref: Logic 8, 
Scientology 0-8, The Book of Basics)

Thus, in rehabbing a release point one is getting the pc to view 
one datum (a time of release from a mass) as compared to another 
datum (a time he was stuck in the mass) and when this is done the 
pc moves out of the mass once again. That is the simplicity of 
what occurs.

To expand on the mechanics involved, it can be described as 
follows:

When a person has been overrun, he is trying to stop the mass or 
thing he has gone back into. The other side to that is the time 
or times he was released from it. These are opposites: the "plus" 
of the mass and the "minus" of the time the mass wasn't there. 
This idea of opposites tends to hang things up.

The idea then behind handling an overrun is to unstabilize this 
plus-minus pair by getting the pc to clearly spot the "minus" 
side of it. When this happens, the "plus" side goes.

When the pc's attention is directed to the points when he was 
released from the mass, he ceases to try and stop the mass and it 
goes. The release state then rehabilitates.

So the mechanism being worked with here is that the mass 
connected with an overrun can be knocked out by spotting the 
release connected with it. It is a very simple principle which 
has important uses in auditing.

             TYPES OF REHABS

There are three types of rehab procedures for use in rehabbing 
releases.

The earliest is Rehab 1965 Style. This is followed by Rehab by 
Counting which I developed in 1968. Later on, in 1971, 1 
developed the Date/Locate procedure.

Each of the three has its uses depending on what it is one is 
trying to rehab.

One does a Rehab '65 Style when one is rehabbing a specific 
point, such as the point a specific former release was attained.

A Rehab by Counting is done when, for instance, a process appears 
overrun in session or when one is rehabbing "releases" such as on 
drugs on the Scientology Drug Rundown, or at any time something 
is likely to have a number of releases connected with it.

A Date/Locate is used when one wants to directly spot the exact 
time and location of a specific incident and thus blow the mass 
connected with it. (Date/Locate is used on the last step of the 
Clear Certainty Rundown to determine the exact point a person 
went Clear. The Date/Locate procedure has many other uses in 
other types of auditing as well, but in rehabbing its most 
frequent use is on the Clear Certainty Rundown, per the above.)

           INDOCTRINATING THE PC

The procedure for doing a rehab is quite simple when one 
understands the theory of it and makes sure the pc does too.

Before doing any rehab or Date/Locate, clear the terms and 
procedure with the pc so that he understands. Use the data in 
this issue to clear the theory of release and rehabs, and to 
clear the procedure to be used -- Rehab '65 Style or Rehab by 
Counting.

Use data in HCOB 15 Nov. 78, DATING AND LOCATING, in 
indoctrinating the pc to the Date/Locate theory and procedure. 
All the terms and steps of the procedure are covered in that 
issue.

The better the pc understands what is going on the smoother it 
will go. Do not skimp this indoctrination step. Any auditing 
efforts can go up in smoke if one tries to audit the pc over 
misunderstoods.

1. Clear the terms below with the pc, using demos and consulting 
the pc's understanding.

   A. RELEASE: 1. A person who has been able to back out of his
      bank. The bank is still there but the person isn't sunk
      into it with all its somatics and depressions. 2. When the
      pc disconnects from the mass in his bank, that is a
      release. When this happens, the pc disconnects from the
      bank to a greater or lesser degree. 3. A person who has
      become free of a difficulty or personal "block" stemming
      from the mind. 4. When you take a thetan out of a mass,
      that is a release.

   B. REHABILITATE: to restore to a former capacity or condition.
      In auditing, this means to do the series of actions in
      session which result in regaining a state of release for
      the pc. Abbreviated "Rehab."

   C. KEY-IN: the action of some part of the reactive mind moving
      in on the person. A key-in occurs when the environment
      around the awake but fatigued or distressed individual is
      similar to some part of the reactive mind. Since the
      reactive mind operates on the equation A=A=A, the present
      time environment becomes identified with the contents of a
      particular portion of the bank and so it activates and
      exerts its influence on the person.

   D. KEY-OUT: the action of the reactive mind or some portion of
      it dropping out of restimulation on the pc.

   E. GRADE: a series of processes culminating in an exact
      ability attained, examined and attested to by the pc. (See
      the Classification, Gradation and Awareness Chart for the
      complete explanation of the different grades.) Auditing
      processes result in a release. The auditing processes of a
      grade, when done, result in the pc attaining the specific
      ability of that grade.

2. Clear "overrun" with the pc, using the section "Overrun" in 
this issue. Have the pc demo an overrun in auditing and in life.

3. Clear with the pc the stable datum on which rehabbing is based 
(under "Theory of Rehabbing" in this issue). Have him demo it 
(using a demo kit) as needed to ensure he's got it.

4. Using a demo kit, clear with the pc the simple mechanics of 
rehabbing (spotting the release connected with a mass). Ref: 
Section on "Theory of Rehabbing" in this issue.

5. Go over with the pc each step of the procedure to be used 
(Rehab '65 Style or Rehab by Counting or Date/Locate, if needed). 
Clear any words regarding these procedures, which have not 
previously been cleared in the pc's auditing. Use a demo kit as 
needed.

6. Cover meter dating with the pc so he understands its purpose 
and how it is done. Use E-Meter Drill 22 to explain it. Ensure 
the pc understands you don't want him dependent on the meter but 
that you will help him, using the meter, if necessary. (Ref: HCOB 
4 Aug. 63, E-METER ERRORS, COMMUNICATION CYCLE ERROR)

Be sure the pc understands the simple basics of rehabbing with no 
questions or confusions or misunderstood terms, before you begin 
any rehab.

Additionally, when doing any type of rehab session it is 
important to ensure the pc's ruds are in before starting.


             REHAB PROCEDURES
      PROCEDURE FOR REHAB '65 STYLE

I. Determine what is going to be rehabbed. This might be a 
release on a process, some other type of former release, or the 
ability of a grade attained by the pc.

   A. For a process, use the question:

      "Were you released on (process)?"

      a. Clear the question on the pc first, omitting the name of
         the actual process.

      b. Then check the question (including the name of the
         actual process) on the meter.

      c. If no read on the question, check Suppress and
         Invalidate.

      d. If the pc says he was released but no read on the
         question, check Suppress or Invalidate. If pc is
         assertive or protesty about having been released, check
         Asserted and/or Protest.

   B. Rehabbing Grades: Data on using '65 Style to rehab grades
      Is covered in the "Rehabbing Grades" section of this issue.

   C. Rehabbing Former Releases: Data on using '65 Style to rehab
      former releases is covered in the "Rehabbing Former
      Releases" section of this issue.

II. When it has been determined that the pc was released on the 
process or that the ability gained for a grade had been attained, 
one proceeds by first finding out when this occurred, per step I 
below, and then continues with the remainder of the rehab steps:

    1. Loosely locate the session or time in which it occurred.
       (Note: This may have to be meter dated if the pc is unable
       to locate when it happened. For this reason, any auditor
       doing rehabs must be adept at E-Meter Drill 22, "E-Meter
       Hidden Date, This Life." Also, see HCOB 2 Aug. 65, RELEASE
       GOOFS, point 4, Meter Misuse.)

       You simply want to determine when. The pc may give you the 
       year, month and day of the release, he may describe it by 
       significance ("The moment I thought to myself, 'That's why 
       I wrecked the car!"'), or he may spot when it occurred by 
       location ("It occurred when I was in session for the first 
       time with Joe in his new auditing room."). The reference 
       for this is HCOB 8 June 63, THE TIME TRACK AND ENGRAM 
       RUNNING BY CHAINS, BULLETIN 2, HANDLING THE TIME TRACK.

       NOTE: The indicators which tell you that the release is 
       rehabilitated are an F/N on the meter and VGIs on the pc. 
       If this occurs on any step of the rehab procedure, simply 
       indicate the F/N and gently end off on that rehab action.

    2. Get in Suppress, Invalidate buttons on the session or
       time.

    3. Get in "Unacknowledged" or "what was unacknowledged."

    4. Indicate anything found to the pc as bypassed charge.

    5. Find the key-in that was keyed out in that time or
       session. (The person went release because something keyed
       out in that time or session.)

    6. When this is found and recognized by the pc, the pc will
       recover the release and the process or grade will be
       rehabilitated.

    7. If this does not happen, find out what keyed in (at some
       point after the release) that ended the release state and
       get it loosely located as in step 1.

    8. Repeat steps 2 to 6 on it.

    9. CONDITIONAL: If, when the above is done, the release still
       has not rehabbed, get the pc to itsa alternately the point 
       of key-out when the pc released and the point of key-in 
       afterwards, one after the other. (Use the meter to guide
       the pc, if necessary, by asking "What's that?" when you see 
       a fall on the needle.) This isn't an alternate /repetitive 
       question -- "What was keyed out then?" / "What was keyed in
       then?" -- but a use of these and any such wording, one 
       after the other, as itsa invitations until the release is 
       regained and F/N, VGIs obtained.

             CHECKING FOR EPs

If one wants to check if the pc has reached the EP of a process 
or if one suspects that the EP may have been reached out of 
session, one can check, "Did anything occur?" per HCOB 5 Dec. 71, 
END PHENOMENAS, and if the EP has been reached it can be rehabbed 
using the Rehab '65 Style. One would never ask leading questions 
or feed the EP to the pc in such situations. Simply check if 
anything occurred.

      PROCEDURE FOR REHAB BY COUNTING

1. Establish there is something to be rehabbed. (Naturally, you 
can't rehab a release if there isn't one. You couldn't rehab a 
process if the pc had never run it.)

The question would vary depending on the situation being 
rehabbed.

   a. If it looks (due to overrun phenomena) as though a process
      has been overrun in session, one could ask, "Have we
      bypassed a release point on this process?"

   b. For rehabbing releases on drugs on the Scientology Drug
      Rundown, one would check, "Did you go release on (drug)?"

2. If there is a release, the question should read. If no read, 
check Suppress and Invalidate. There must be a read either on 
checking the question or on the pc's origination that there is a 
release there, before proceeding with the rehab.

3. If no read but the pc says he was released, check if the 
release has been Suppressed or Invalidated. If the pc is 
asserting release or being protesty about it, check Asserted 
and/or Protest.

4. Sometimes the pc will F/N simply on spotting he was released. 
This can be quite common especially when the pc's ruds are in and 
the auditor's TRs are smooth. An F/N with good indicators tells 
you that the rehab is complete and the mass has keyed out or the 
state has been rehabilitated.

5. If no F/N on spotting there was a release, ask the pc how many 
times he was released. Get him to count the number of times and 
when he gets it he will F/N.

6. Sometimes the pc can't get the number and the auditor can then 
use the meter to count how many times and get it that way. He can 
ask the pc if he has some idea of the approximate number of times 
and then use "More than ______?" / "Less than ______?" He uses 
the tech of E-Meter Drill 22 to establish the general range of 
number of times. He would then count to the pc. ("Were you 
released on ______ 10 times? 11? 12?" etc.)

The correct number of times will read and, when indicated, will 
F/N.

Rehab by Counting is a simple procedure but it can get messed up 
by an uncertain attitude on the part of the auditor or by rough 
auditor TRs, so be sure you are confident and well drilled.

       BRIDGING FROM REHAB BY COUNTING
                TO '65 STYLE

If, even with the ruds in, doing a Rehab by Counting doesn't F/N, 
one can bridge over into a Rehab '65 Style and rehab it that way. 
Doing a Rehab '65 Style will clean up any bypassed charge on the 
release and allow it to rehab.

If on the Rehab by Counting the pc had said he was released 
several times, one would have to find the primary release point 
(the one "that is most real to him," or when he "had the biggest 
win," etc.) in order to do the Rehab '65 Style steps on that 
release point. Handled smoothly in this way, you will be able to 
rehabilitate the release, with F/N, VGIs.

           DATE/LOCATE PROCEDURE

The Date/Locate procedure is very thoroughly covered in HCOB 15 
Nov. 78, DATING AND LOCATING, and thus is not repeated here. It 
is based upon the fundamental principles of rehab tech, but the 
additional theory and full Date/Locate procedure contained in 
HCOB 15 Nov. 78 must be understood and drilled well, before it is 
done on any pc.

        ADDITIONAL DATA ON SPECIFIC
         USES OF REHAB PROCEDURES

If one is to handle rehabs, he must know the fine differences 
involved in the application of rehab tech to each type of thing 
to be rehabbed.

For example, the rehabbing of grades and the rehabbing of former 
releases differ from each other and they also differ slightly in 
some of their steps from the rehabbing of specific processes as 
covered earlier in this issue.

For this reason each is taken up separately here in its own 
section.

            REHABBING GRADES

The rehabilitation of any grade is done on the basis of actual 
auditing having been done to the end product of the specific 
Ability Gained for the grade on all flows. (Note: Pcs should be 
quadded up by the time they receive their Grades.)

One does not rehab a grade by checking "Did anything occur?" or 
"Were you released on Grade ______?" Of course something would 
have occurred on the grade 	and the pc would have released each 
time a process or a flow on a process of the grade F/Ned. This is 
not what you're looking for.

The end phenomena of a grade is the attainment of an ability by 
the pc which he did not previously have. Each level of the Grade 
Chart results in a specific ability gained by the pc when he does 
that particular grade. These are expressed on the Grade Chart in 
the "Ability Gained" column.

The specific ability for each of the four flows of a grade is 
listed in HCOB/HCO PL 23 Oct. 80R II, CHART OF ABILITIES GAINED 
FOR LOWER LEVELS AND EXPANDED LOWER GRADES. These are what you 
are interested in finding out and rehabbing, if they have been 
attained.

You want to determine that the pc has gained the ability for each 
flow of the grade when you are rehabbing. It's not: Did he get 
his Grade 0 ability? It's: Is he willing for others to 
communicate to him on any subject? Does he no longer resist 
communication from others on unpleasant or unwanted subjects? 
Yes? Good, he's made it on Flow I of Grade 0.

Does he have the ability to communicate freely with anyone on any 
subject? Is he free from or no longer bothered by communication 
difficulties, and no longer withdrawn or reticent? Does he like 
to outflow? If so, he's attained the ability on Flow 2 of Grade 
0.

One checks each flow of a grade for the ability of that flow in 
this way. If the pc says he can't, or if he reads on the meter as 
being unable to communicate freely to others, for example, then 
you know he is not complete on that grade. He would need to have 
an FES done at least as far back as the beginning of that grade 
and any errors found corrected, and then more processes for that 
grade run on all flows until the ability gained had been 
genuinely attained. Further data about handling the pc who hasn't 
made a grade is contained in C/S Series 4.

A Dianetics pc who couldn't honestly say he was a well and happy 
human being would need more somatic items run out R3RA.

One would never try to rehab a grade the pc had never really been 
run on or, for instance, Q-and-A with a pc who asserted he was a 
Grade 2 Release because he went to confession as a youth. The 
Abilities Gained of the Grades are attained only by auditing on 
the various processes of each grade. The results of well-run 
grades are light-years above anything that other fields or 
practices can offer, so don't sell them short by omitting or 
quickying them.

The procedure, then, for rehabbing a grade is as follows:

1. Establish from folder study that the pc has run the processes 
of the grade on all flows in the first place. There should be 
some evidence in the folder that the pc has attained the grade, 
whether previously declared or not. He should have run enough 
processes for this to be evident.

2. Show the pc (with pc on the meter) the written statement of 
the Ability Gained for Flow I of the grade, and have him read it. 
(Ref: HCOB/HCO PL 23 Oct. 80R II, CHART OF ABILITIES GAINED FOR 
LOWER LEVELS AND EXPANDED LOWER GRADES)

3. Then check with the pc as to whether he has attained (or "can 
do") the ability for that flow of the grade, as stated in HCOB /
HCO PL 23 Oct. 80R II.

4. If he has attained it, rehab it by Rehab '65 Style.

5. Repeat steps 2 and 3 on the Ability Gained for each of the 
remaining flows (Flows 2, 3 and 0) of the grade.

6. If the pc has attained the ability on each flow of the grade, 
he is a valid Release on that grade.

7. If the pc doesn't have the Ability Gained for one or more of 
the flows of the grade, he doesn't have the abilities of the 
grade. The processes (and the flows) he ran on it would have to 
be FESed to locate any errors. The errors found would have to be 
corrected and any unflat process flattened. Also, any missed 
processes for that grade would need to be run until the pc really 
had the Ability Gained for each flow of the grade.

         REHABBING FORMER RELEASES

Rehabbing former releases came into being in 1965 and was done 
most frequently in that year and the years immediately following 
it, after the Grades had been established. At that time it was 
necessary to clear up and get acknowledged the former releases a 
pc may have had during his processing in the previous years, and 
to determine that he had been released on each grade before he 
went onto Power and Clearing.

It is still a very valid tech that is used when needed.

It may in some instances be done, at the adjudication of the C/S, 
where a case is having trouble or is bogged and the C/S suspects 
from folder study that the case may be hung up on former release 
points.

In genning the pc in to this action, ensure he understands what 
is being looked for. Although one uses Rehab '65 Style, the 
action is not the same as rehabbing a grade or even exactly the 
same as rehabbing a process. Here you are looking for times in 
the pc's auditing history, recent or distant, when he felt good 
in sessions. This would not necessarily have to be a specific EP 
of a process the pc ran or the EP of a particular grade. 
Rehabbing former releases is not limited by reference to any 
specific process or grade. Also, when the pc is asked about an 
earlier release, he may offer up a time he felt released from 
something in life. If so, this would be checked and handled just 
as any other release point, as in this action you are going to 
rehab any and all validly reading release points the pc may 
offer. When a former release is found, it is rehabbed by the '65 
Style.

The procedure for rehabbing former releases is:

1. Ensure the pc's ruds are in and that he has been through steps 
1-6 of the section "Indoctrinating the Pc," in this issue.

2. Have the pc demo the idea of former releases as it applies to 
auditing and to life until he's got it.

3. R-factor the pc that you are going to rehab any former 
releases he may have had.

4. Clear the question: "Have you been released earlier?" Then 
check the question.

5. If you get a read on clearing or checking the question, find 
out what the release was on.

   a. If no read on the question when cleared or checked, check 
      Suppress and Invalidate.

   b. If pc says he was released earlier but no read on the
      question when cleared or checked, check Suppress or
      Invalidate. If the pc is assertive or protesty about
      having been released, check Asserted and/or Protest.

6. When it has been determined that the pc has been released 
earlier, one then proceeds per step I of Rehab '65 Style 
instructions until one gets an F/N and rehabilitation of the 
former release.

7. One then checks for any other former releases by checking, "Is 
there another time you were released earlier?" and handles per 
steps 5 and 6 above.

8. Repeat step 7 as long as the pc has former releases to rehab.

9. Conditional: If on steps 5a or 5b the meter doesn't read or 
ceases reading even after Suppress, Invalidate, Asserted and/or 
Protest are checked, or if an ARC break needle turns on while 
doing the rehabs, one checks for and handles any ARC breaks which 
may be present in the session or connected with the thing you are 
trying to rehab.

After handling any ARC breaks, recheck for former releases and 
handle until the auditor, pc and meter are in agreement that any 
former releases have been rehabbed and that there are no ARC 
breaks preventing any former release from reading. It may be 
necessary to also check and handle the other rudiments (PTP and 
Missed Withholds) to ensure there is nothing preventing any 
former release from reading.

10. Conditional: If the pc has a big win in rehabbing former 
releases, one would let him have his win and end the session. 
When sessions are resumed, one would then check for and handle 
any remaining former releases.

When all the pc's former releases have been rehabbed, the action 
is complete.


   ADVICE TO AUDITORS AND C/Ses ON REHABS

             Meter Dependence

In using the meter on a rehab of any sort, one does not want to 
get into a situation where the pc is made dependent on the meter 
for obtaining data. One uses the meter in a rehab only when the 
pc is unable to come up with the data needed. In getting the 
number of times released on a process, for instance, the auditor 
would get the pc to establish the number of times released and 
only if the pc could not get it would the auditor use the meter 
to find the number of times released. This all comes under 
increasing the pc's certainty of his data and is best expressed 
in HCOB 4 Aug. 63, E-METER ERRORS, COMMUNICATION CYCLE ERROR.

           RELEASE REHAB BLOCKS

There are three main reasons why a release rehab on a subject or 
action might hang up:

   1. Out-ruds.

   2. The pc was never released on it in the first place.

   3. There is something earlier on the track which was similar to 
      it. (For example, in rehabbing a drug, the pc may have been 
      released on a similar drug back on the track.)

1. Out-Ruds: When a rehab is not going to an F/N, you will 
usually find that it is being done over an out-rud. This can be 
(a) an out-rud on the subject of the rehab or (b) an out-rud in 
the rehab session itself.

While you are rehabbing, you watch the pc to make sure his good 
indicators remain in because you could get an ARC break needle on 
it and not notice it. An ARC break needle is easy to establish 
because you've got bad indicators with it.

Where you have bad indicators with an ARC break needle, just put 
in the ruds on the subject.

EXAMPLE: The auditor is rehabbing releases in the taking of ether 
and it won't F/N. The auditor could ask, "In the taking of ether 
was there any ARC break?" One can put in the ARC break, Problem 
and Missed Withhold ruds, if they are reading.

The out-ruds might have occurred before the point of release, and 
this can be checked for as well.

The actual mechanism which you're using is: If it won't rehab and 
the F/N is an ARC break needle, then there's trouble afoot of 
some kind or another. Just put in the ruds on the subject.

If there is roughness in the rehab session, an ARC break needle 
could occur. If so, get the ruds in on the session and complete 
the rehab.

2. The pc was never released on it in the first place: A release 
rehab on a subject or action might hang up because the person 
never did go release on it. In other words, the F/N does not 
rehab because it did not happen in the first place. If it is a 
process or grade, the handling would be to run it to EP

3. Earlier-Similar: Sooner or later you are going to find someone 
who won't release during a rehab on a specific subject or action. 
The overrun is so overrun that the releases are no longer 
available in it.

You can put in the ruds in connection with that subject or action 
(or the session if that is needed). But if it just won't rehab at 
all, there is still a way you can handle it: Ask the pc if there 
was anything earlier on the track that was similar to the subject 
or action.

EXAMPLE:

Auditor: "Well, did you take anything earlier on the track that 
was similar to kerosene?"

PC: "Oh, yes, yes. We used to take balderdash in the old days, I 
just remembered. Yes." (F/N)

Auditor: "Thank you. Your needle is floating."

                 --------

Rehabs are very simple to do provided the auditor's comm cycle is 
not rough or distracting and both he and the pc understand what 
is being done on a rehab and how the procedures go. The action is 
one of destimulation not restimulation. It is done with a light 
touch and is a smooth action. One doesn't get into forcing the pc 
on a rehab.

Drilling the different rehab procedures must be a part of any 
high crime checkout on this bulletin so that the auditor can 
confidently handle any situation that might arise during a rehab.

The best way to run a session is to be so sharp as an auditor 
that you never let the pc overrun in the first place. But should 
this occur or should you inherit a pc that another auditor has 
overrun, or should life and livingness knock out a release state, 
this issue lays out the steps for restoring any type of release.


L. RON HUBBARD
Founder

Revision assisted by
LRH Technical Research
and Compilations

LRH:RTRC:dk.gm





